Wireless network device configured for adjustable positioning

ABSTRACT

Systems, methods, and devices relating to a wireless network device configured for adjustable positioning are described herein. In an example, a network device comprises a body and a bendable element configured to carry electrical power to the body and components therein. The body houses an antenna and transceiver configured for wireless communication. The bendable element, attached to the body of the network device, is configured for adjustable positioning such that a position of the bendable element is substantially maintained when the positioning force is removed. A facing of the antenna within the body may be based on the positioning of the bendable element.

BACKGROUND

Under an Internet of Things (IoT) or similar model, a wide variety ofobjects may be equipped with embedded electronics that enable theseobjects to collect and exchange data across a communication network. Asan example, a home gas meter may be configured with electronics thatcollect and store the home's gas usage. The gas usage data may beperiodically uploaded to the utility company's systems. An IoT (orsimilar) device may also find use in home automation. For example, a“smart” light fixture or even light bulb may be configured to turn on oroff according to an external control signal received by the lightfixture or bulb. The term “end node” may be used to refer to theseembedded electronics, IoT devices, or the like.

In many cases, wireless communication is used to send data to and/orreceive data from an end node. For example, end nodes often wirelesslycommunicate with a network device (e.g., a gateway) to effectuatecommunication with other upstream systems. Yet there are challenges inimplementing wireless communication between an end node and anassociated network device. For example, such wireless communication maybe hampered by the distance between the end node and network device,intervening physical objects or structures that absorb the wirelesssignal, or electromagnetic interference. Further exacerbating thesechallenges is the fact that an end node is often unconnected to anexternal power source and must instead rely on its own battery power,which may be quite limited.

These and other shortcomings are addressed in the present disclosure.

SUMMARY

Systems, methods, and devices relating to a wireless network deviceconfigured for adjustable positioning are described herein. A networkdevice may comprise a body and a bendable element configured to carryelectrical power to the body and components therein. The body may housean antenna and transceiver configured for wireless communication. Thebendable element, attached to the body of the network device, may beconfigured for adjustable positioning such that a position of thebendable element may be substantially maintained when the positioningforce is removed.

A facing of the antenna within the body may be based on the positioningof the bendable element. The performance of the antenna in receivingand/or transmitting RF signals may be based on the positioning of theantenna.

The bendable element may comprise a plug configured to receiveelectrical power from a power source. The plug may be connected to aport of the power source. This connection may physically support, atleast in part, the network device. The plug may comprise a USB plug andthe port of the power source may comprise a USB port.

The bendable element may be configured to adjust the position of thebody corresponding to a length-wise dimension of the body, a directioncorresponding to a width-wise dimension of the body, and/or a directioncorresponding to a height-wise dimension of the body. The bendableelement may be additionally or alternatively configured to adjust theorientation of the body with respect to a length-wise axis of the body,a height-wise axis of the body, and/or a width-wise axis of the body.

The network device may be configured as an LPWAN gateway. The networkdevice so-configured may communicate, via the antenna, with one or moreend nodes of the LPWAN. The network device may be configured tocommunicate with the one or more end nodes via a low-power protocol,such as a protocol comprising at least one of Zigbee, Z-Wave, Wi-FiHaLow, NB-IoT, DASH7, Sigfox, or LoRa.

A network device may comprise a body and a printed circuit board (PCB)housed within the body. The PCB may comprise an antenna configured toenable radio frequency (RF) communication. The network device mayfurther comprise a bendable element comprising an elongate bendablesection and a plug configured to receive electrical power. A proximateend of the bendable section may be attached to and physically supportthe body. A distal end of the bendable section may be configured withthe plug. The bendable section may comprise a power transmission elementthat electrically connects the plug with a power unit associated withthe PCB. The bendable section may comprise a malleable element via whicha variable positioning of the bendable section is substantiallymaintained upon removal of a positioning force.

This Summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This Summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used to limit the scope of the claimed subject matter. Furthermore,the claimed subject matter is not limited to limitations that solve anyor all disadvantages noted in any part of this disclosure.

BRIEF DESCRIPTION OF DRAWINGS

The accompanying drawings, which are incorporated in and constitute apart of this specification, illustrate embodiments and together with thedescription, serve to explain the principles of the systems, methods,and devices:

FIG. 1 illustrates a block diagram of a communication system.

FIG. 2 illustrates a block diagram of a communication system.

FIG. 3 illustrates a partial cut-away view of a network device.

FIG. 4 illustrates a cross-sectional view of a bendable element of anetwork device.

FIG. 5 illustrates a perspective view of a network device.

FIG. 6 illustrates a perspective view of a network device.

FIGS. 7A-7D illustrate side views of network device positionings.

FIG. 7E illustrates a top-down view of a network device positioning.

FIG. 8 illustrates a block diagram of a computing device.

Aspects of the disclosure will now be described in detail with referenceto the drawings, wherein like reference numbers refer to like elementsthroughout, unless specified otherwise.

DETAILED DESCRIPTION

Systems, methods, and devices relating to a wireless network deviceconfigured for adjustable positioning are described.

FIG. 1 illustrates a system 100 in which the present systems, methods,and devices may be implemented. The system 100 comprises a firstcomputing device 110 in communication with a second computing device 108via a network 112 and a network device 104. The network device 104 maybe configured for adjustable positioning to achieve favorable wirelesssignal reception and/or transmission. For example, the network device104 may be configured with an antenna within the network device's 104body. The facing of the antenna may be adjusted by bending and/ortwisting the bendable element 120 to a desired position. Electricalpower from a power source 106 may be provided to the network device 104via the bendable element 120. The system 100 may be configured, at leastin part, as a low power wide area network (LPWAN) but is not so limited.The network device 104, including the bendable element 120, may comprisea “dongle” device, such as a universal serial bus (USB) dongle device.

The network device 104 may be configured to effectuate communicationbetween the first computing device 110 and the network 112, includingthe second computing device 108 and other computing devices connected tothe network 112. Communication between the network device 104 and thefirst computing device 110 is generally contemplated to be wireless. Thenetwork device's 104 communications to the network 112 may be wired,wireless, or a combination thereof. The network device 104 may comprisea router or gateway configured to receive communication data from thefirst computing device 110 and transmit (e.g., route) the data to thenetwork 112 and the second computing device 108. Conversely, the networkdevice 104 may be configured to receive communication data from thenetwork 112, such as that from the second computing device 108, andtransmit (e.g., route) the data to the first computing device 110. Thenetwork device 104 may be additionally or alternatively realized as aresidential gateway or router, such as a cable modem, DSL modem,wireless router, or wireless access point. The network device 104 may berealized as an LPWAN gateway configured to communicate with low-poweredsensors, IoT devices, or embedded electronics (i.e., “end nodes”). Thenetwork device 104 configured as an LPWAN gateway may be located at aresidence.

The first computing device 110 may be configured as an end node, such asan end node in an LPWAN. The first computing device 110 may be in theform of embedded electronics of another device or object. The firstcomputing device 110 may operate using only battery power (e.g., thefirst computing device's 110 own battery power). The first computingdevice 110 may be configured generally to consume minimal power. Thefirst computing device 110 may comprise a sensor configured to collectdata, such as data associated with the first computing device's 110surroundings. The first computing device 110 may comprise an actuatorconfigured to effectuate an action or function (e.g., a pre-determinedaction or function) based on a received communication and/or collecteddata. The first computing device 110 may be configured to communicatedata (e.g., the collected data) to the network device 104. For example,the first computing device 110 may communicate data (e.g., a message)based on data collected or measured by the first computing device 110.

The first computing device 110 may comprise a personal computer, alaptop computer, a tablet computer, a mobile device (e.g., a cell phoneor smartphone), or other type of computing device. The first computingdevice 110 may be configured with an antenna and a receiver and/or atransmitter, which may be used to wirelessly communicate with thenetwork device 104. The first computing device 110 may be configured forin-bound communication only, out-bound communication only, orbi-directional communication.

The network device 104 may be configured for wireless communication withthe first computing device 110 via an antenna of the network device 104.The network device 104 and the first computing device 110 may form partof a wireless local area network (WLAN), a wide area network (WAN), or awireless personal area network (WPAN). The network device 104 and thefirst computing device 110 additionally or alternatively may form partof an LPWAN. The network device 104 and the first computing device 11may wirelessly communicate with one another according to one or more ofa variety of specifications, standards, or protocols. For example, thenetwork device 104 and the first computing device 110 may communicationvia Wi-Fi, such as according to one of the various IEEE 802.11standards. The network device 104 and the first computing device 110 maycommunication via Bluetooth, Zigbee, Z-Wave, Wi-Fi HaLow, Narrowband IoT(NB-IoT), DASH7, or Sigfox. The network device 104 and the firstcomputing device 110 may communicate via LoRa and/or LoRaWAN protocols.In a low power implementation, the network device 104 and the firstcomputing device 110 may communicate with one another using, forexample, one or more of the aforementioned Zigbee, Z-Wave, Wi-Fi HaLow,NB-IoT, DASH7, Sigfox, or LoRa protocols.

The network device 104 may communicate with the network 112 via wirelesscommunication, wired communication, or a combination thereof. Asexamples of wired communications, the network device 104 maycommunication with the network 112 via ethernet, a cable internetconnection, or a DSL connection. As examples of wireless communications,the network device 104 may communicate with the network 112 via Wi-Fi(or other wireless protocol described herein) or a cellular connection.The protocol and/or medium that the network device 104 uses tocommunicate with the first computing device 110 may be different thanthe protocol and/or medium used by the network device 104 to communicatewith the network 112.

The network device 104 (e.g., configured as a gateway) may be configuredto communicate with a second network device (e.g., a router, Wi-Firouter, wireless access point, cable modem, or DSL modem) over a wiredor wireless connection. The second network device may be co-located withthe network device 104, such as at a residence. The network device 104may communicate with the first computing device 110 using a low-powerfirst protocol (e.g., LoRa, Zigbee, Z-Wave, Wi-Fi HaLow, NB-IoT, DASH7,or Sigfox). The network device 104 may communicate with the secondnetwork device using a different, second protocol (e.g., ethernet orWi-Fi). The second network device may route or otherwise transmit datareceived from the network device 104 to the network 112, such as via acable internet connection, a DSL internet connection, or a cellularconnection.

The network device 104 may be configured for cellular communication witha cellular network in the network 112. The network device 104 maycommunicate with the first computing device 110 using a low-power firstprotocol (e.g., LoRa, Zigbee, Z-Wave, Wi-Fi HaLow, NB-IoT, DASH7, orSigfox). The network device 104 may communicate data received from thefirst computing device 110 to the network 112 via the network device's104 cellular connection (e.g., via a cellular communication protocol) tothe network 112.

The network device 104 may be configured with a bendable element 120that is connected to the power source 106 supplying the network device104 with electrical power. The bendable element 120 may be configured tosubstantially maintain its shape and position after the bendable element120 is bent in any of various directions, included twisting. Thebendable element 120 may comprise one or more bendable cables or wireswithin the bendable element 120. The bendable cables or wires may bemade from a material with a high degree of ductility and/ormalleability, such as aluminum, an aluminum alloy, copper, or a copperalloy. The bendable element 120 may additionally or alternativelycomprise one or more power transmission elements, such one or more powerwires or cables embedded within the bendable element 120. The powertransmission element of the bendable element 120 may transmit electricalpower from the power source 106 to the network device 104.

The connection of the bendable element 120 with the power source 206 mayphysically support the network device 104, at least in part. Thebendable element 120 and the power source 206 may be configured withcomplementary interfaces (e.g. hardware interfaces) via which electricalpower is conducted. Such complementary interfaces may physically supportthe network device 104 when the network device 104 is connected to thepower source 106. For instance, the bendable element 120 may beconfigured with a plug and the power source 106 may be configured with acomplementary port. The bendable element 120 may be configured with aUSB plug and the power source 106 may be configured with a USB port.

The power source 106 may be realized in any one various of forms. Thepower source 106 may comprise a computing device, such as a personalcomputer, a laptop computer, or a rack-mounted computing device. Thepower source 106 may comprise a set-top box (e.g., a cable televisionbox or digital media player). The power source 106 may comprise anetwork device, such as a wireless router, wireless access point, cablemodem, or DSL modem. The network device 104 may communicate with thenetwork 112 via this same network device to which the bendable element120 is connected. For example, the bendable element 120 may be pluggedinto a wireless router to receive power and the network device 104 maycommunicate with the network 112 via wireless communication with thewireless router. As noted, the computing device, the set-top box, or theother network device may comprise a port into which the bendable element120 of the network device 104 may be inserted to physically support thenetwork device 104 and provide the network device 104 with power.

The power source 106 additionally or alternatively may comprise a“charger unit.” The charger unit may comprise a port configured toreceive a plug of the bendable element 120 and a power plug configuredto receive power from a power socket, such as an AC power socket. An ACpower socket may comprise a wall socket or power strip socket, forexample. The power plug of the charger unit may be integrated with thebody of the charger unit and/or rigidly affixed to the body of thecharger unit. For example, a cube-shaped charger unit may comprise aport on one side of the charger unit and power plug prongs of anopposite side of the charger unit. The charger unit may comprise a USBcharger unit, such as a USB wall charger unit.

The second computing device 108 may comprise a server or multipleinterconnected servers. The second computing device 108 may beassociated with the first computing device 110. The second computingdevice 108 may receive data (via the network device 104 and the network112) from the first computing device 110 and perform one or morefunctions based on the received data. The second computing device 108may generate a website that presents at least some of the received dataand/or information based on the received data. The second computingdevice 108 may receive multiple sets of data from the first computingdevice 110 over a period of time and perform data analysis on theaggregated data. The second computing device 108 additionally oralternatively may transmit data (via the network 112 and the networkdevice 104) to the first computing device 110, such as an instructionfor the first computing device 110 to perform some action or function.The second computing device 108 may comprise an application serverassociated with the first computing device 110.

FIG. 2 illustrates a system 200 in which the systems, methods, anddevices described herein may be implemented. The system 200 may comprisean LPWAN and associated systems and devices. The system 200 may beimplemented according to one or more specifications, protocols, and/orstandards associated with an LPWAN. For example, the system 200 may beimplemented according to the LoRaWAN specification. The system 200 maybe the same as or similar to the system 100 of FIG. 1 in some aspects.The system 200 may comprise a gateway 204 configured for wirelesscommunication with one or more end nodes 210. The gateway 204 maycomprise a bendable element 220 that may be used to selectively adjustthe positioning and orientation of the gateway 204 and its antenna, aswell as to supply power to the gateway 204 from a power source 206. Thegateway 204 may be configured as a dongle, such as a USB dongle. Thegateway 204 may be in mutual communication via a backhaul network 212with a radio controller 214, which, in turn, is in mutual communicationwith one or more application servers 208.

An end node 210 may be similar to or the same as the first computingdevice 110 of FIG. 1 in some aspects. An end node 210 may comprise a lowpower end node. An end node 210 may be battery-operated. An end node 210may be realized as a stand-alone device or as embedded electronics. Anend node 210 may be configured to collect and store data, such as thatmeasured or determined by a sensor of the end node 210. For example, anend node 210 may comprise a sensor configured to measure air pollutionparticles. The end node 210 may wirelessly transmit the air pollutiondata to the gateway 204 for ultimate delivery to an application server208. Additionally or alternatively, the end node 210 may wirelesslytransmit data indicating that the measure of air pollution particlessatisfies a threshold (e.g., exceeds a threshold). An end node 210 maycomprise an actuator configured to effectuate some action or function,such as based on data (e.g., an instruction) received via the gateway204. An actuator need not necessarily be a physical actuator, but may beadditionally or alternatively a logical actuator or an electronicactuator. An end node 210 may comprise electronics embedded in a coffeemaker. This end node 210 may receive data indicating an instruction forthe coffee maker to begin to brew coffee.

An end node 210 may wirelessly communicate with the gateway 204 onlyperiodically, such as to minimize power consumption. For example, an endnode 210 may activate its communication functionalities only duringcertain time windows of the day. An end node 210 may be configured totransmit data collected or determined by the end node 210 but notreceive data (e.g., payload data). An end node 210 may be configured toreceive data but not transmit data (e.g., not transmit collected ordetermined data, or payload data generally). An end node 210 may beconfigured to both receive data from the gateway 204 and transmit datato the gateway 204.

The gateway 204 may comprise a network device configured for wirelesscommunication with the end nodes 210. The gateway 204 may be the same asor similar to the network device 104 of FIG. 1 in some aspects. Thegateway 204 may comprise an LPWAN gateway. The gateway 204 and the endnodes 210 may be configured for wireless communication using an LPWANprotocol, such as Zigbee, Z-Wave, Wi-Fi HaLow, NB-IoT, DASH7, Sigfox, orLoRa protocols. The gateway 204 may communication with the end nodes 210using a different protocol (e.g., one or more of the aforementionedLPWAN protocols) than the protocol (or medium altogether) used by thegateway 204 to communicate with the backhaul network 212 (e.g., Wi-Fi,ethernet, or cellular protocols). Communications between the gateway 204and the end nodes 210 may be in accordance with a low-power scheme. Forexample, the gateway 204 and the end nodes 210 may communicate with oneanother only during pre-defined time intervals.

In a similar manner as the network device 104 of FIG. 1, the gateway 204may be configured with the bendable element 220. The bendable element220 may be the same as or similar to the bendable element 120 of FIG. 1.The bendable element 220 may be adjusted to put the gateway 204 (e.g.,the body of the gateway 204) in a desired position and orientation. Theposition and orientation of the gateway 204 may give optimal or improvedreception for the antenna within the body of the gateway 204. Thebendable element 220 may be configured such that a new positioningand/or orientation of the gateway 204 is held after the bendable element220 is repositioned. The bendable element 220 may be configured with oneor more power transmission elements, such as wires or cables, to carryelectrical power from the power source 206 to the gateway 204.

The bendable element 220 may be connected to (e.g., plugged into) thepower source 206. The connection may provide a mounting point for thegateway 204, as well as provide the gateway 204 with electrical power.For example, bendable element 220 may comprise a plug and the powersource 206 may comprise a port configured to receive the plug. The plugand port may comprise a USB plug and USB port, respectively. The powersource 206 may be similar to or the same as the power source 106 of FIG.1 in some aspects. The power source 206 may comprise a computing and/ornetwork device. The power source 206 may comprise a wireless router orgateway, a wireless access point, a cable modem, or a DSL modem. Thegateway 204 may communicate with the backhaul network 212 via the powersource 206 so configured. The power source 206 may comprise a chargerunit. The charger unit may comprise a wall charger unit, such as a USBwall charger unit. The charger unit may comprise a power plug, such as apower plug configured for connection to an AC power socket.

As indicated, the system 200 may comprise the radio controller 214. Theradio controller 214 may be configured as an LPWAN radio controller,such as a LoRaWAN radio controller. The radio controller 214 may beembodied as one or more interconnected computing devices, such asservers and/or networking devices. The radio controller 214 mayfacilitate and coordinate communication between the end nodes 210 andthe application servers 208. For example, the interaction between thegateway 204 and the end nodes 210 may be coordinated by the radiocontroller 214. As such, the radio controller 214 may provideintelligence relating to data packets transmitted between the end nodes210 and the gateway 204, including, as some examples, schedulingacknowledgments, performing security and data integrity functions, andmanaging data transmission rates between the end nodes 210 and thegateway 204.

The application servers 208 may be similar to or the same as the secondcomputing device 108 in some aspects. An application server 208 may beassociated with one or more end nodes 210 and receive data from anassociated end node 210. The application server 208 may perform one ormore functions based on the received data. Additionally oralternatively, an application server 208 may transmit data to anassociated end node 210, such as instruction for the end node 210 toimplement one or more functions.

FIG. 3 illustrates a cutaway view (indicated by the various dottedlines) of a network device 304 (e.g., the network device 104 of FIG. 1or the gateway 204 of FIG. 2) comprising a body 330 and a bendableelement 320 (e.g., the bendable element 120, 220 of FIGS. 1 and 2,respectively). The network device 304 may be configured as a gatewaywithin an LPWAN. The network device 304 may be configured to wirelesslycommunicate with one or more low power end nodes of the LPWAN. Thebendable element 320 may comprise a bendable section 332 and a plug 334.The body 330 may house a printed circuit board (PCB) 336 comprising aplurality of components configured to implement the various functions ofthe network device 304. For example, the components of the PCB 336 mayimplement functions of the network device 304 as described in relationto the network device 104 of FIG. 1 and/or the gateway 204 of FIG. 2.

The PCB 336 housed within the body 330 may comprise a processor 346 andmemory 344. The processor 346 may effectuate various functions of thenetwork device 304. For example, the processor 346 may implementinstructions stored in the memory 344. The memory 344 may additionallyor alternatively store data, such as data collected from an LPWAN endnode and received by the network device 304. The PCB 336 may comprise apower unit 342 that receives electrical power to operate the networkdevice 304. The power unit 342 may be connected to a power transmissionelement 348 of the bendable element 320 via which the power unit 342receives power from a power source (e.g., the power source 106, 206 ofFIGS. 1 and 2, respectively).

The PCB 336 may comprise an input/output (I/O) interface 352. The I/Ointerface 352 may comprise a wired interface, such as an ethernetinterface or USB interface. The I/O interface 352 may be used toconfigure the network device 304 to perform the desired functions. Forexample, the instructions stored in the memory 344 and executed by theprocessor 346 may be received via the I/O interface 352.

The PCB 336 may comprise a transceiver (TX/RX) 340 and associatedantenna 338 configured to perform wireless communication, such as withone or more end nodes. Such wireless communication may be according toan LPWAN protocol, such as LoRa, Zigbee, Z-Wave, Wi-Fi HaLow, NB-IoT,DASH7, or Sigfox. The transceiver 340 and antenna 338 may communicateusing spread spectrum techniques, such as chirp spread spectrum. Theantenna 338 may comprise a directional antenna. The antenna 338 may beintegrated with the PCB 336. The antenna 338 may comprise a microstripantenna, such as a patch antenna. The antenna 338 may comprise aninverted-F antenna, such as a planar inverted-F antenna (PIFA). Theplanar surface of a PIFA (or other antenna) may correspond with (e.g.,be parallel with) the planar surface of the PCB 336 to which the variouscomponents are mounted or integrated.

As indicated, the network device 304 may comprise a bendable element 320via which the network device 304 is mounted and receives power. Thebendable element 320 may be selectively manipulated (e.g., bent,twisted, etc.) to set the position and/or orientation of the body 330,as well as the facing of the antenna 338 housed therein. The body 330may be positioned and/or oriented to provide optimal or improved RFtransmission and/or reception by the antenna 338. For example, anadjusted position and/or orientation of the body 330 may provide animproved wireless signal for the antenna 338. Improvement to thewireless signal may be with respect to signal strength (as received bythe antenna 338) and/or signal noise. An adjusted position and/ororientation of the body 330 may optimize or improve the RF signal spreadof the antenna 338. An adjusted position and/or orientation of the body330 may avoid interference at the antenna 338 caused by other nearbyantennas. The position and/or orientation of the body 330 may also beadjusted according to the physical setting in which the network device304 and an associated power source are installed. For example, the powersource may be installed almost flush to an adjacent wall. The body 330may be positioned and/or oriented so as to fit into the narrow spacebetween the power source and the wall.

The bendable element 320 may comprise a bendable section 332 and a plug334. As discussed in relation to the plug of the bendable element 120,220 of FIGS. 1 and 2, respectively, the plug 334 may connect to or beinserted into a port of a power source (e.g., the power source 106, 206of FIGS. 1 and 2, respectively). The plug 334 may be configured as a USBplug and the port of the power source may be configured as a USB port.The USB plug may be configured according to one or more of the USB 1.x,USB 2.0, USB 3.x, or USB4 specifications. The USB plug may comprise astandard type A plug, a standard type B plug, a standard type C plug, amini A plug, a mini B plug, a mini AB plug, a micro A plug, a micro Bplug, or a micro AB plug. The bendable element 320 may comprise othertypes of connectors in addition to or as an alternative to the plug 334.For example, the bendable element 320 may comprise a port that connectsto a plug of a power source.

The bendable section 332 of the bendable element 320 may comprise one ormore malleable elements 350. The one or more malleable elements 350 maybe configured with circular, square, or rectangular cross sections. Theone or more malleable elements 350 may be in a flat or ribbonconfiguration. The one or more malleable elements 350 may in the form ofa wire. The malleable elements 350 may span at least the majority of thelength of the bendable section 332. For example, as shown in FIG. 3, themalleable elements 350 may span the entire length of the bendablesection 332. The malleable elements 350 may be formed from aluminum, analuminum alloy, copper, or a copper alloy. The bendable section 332 maycomprise a power transmission element 348 configured to carry electricalpower from a power source (via the plug 334) to the power unit 342 inthe body 330 of the network device 304. The power transmission element348 may comprise a wire, a plurality of wires, or a cable, as someexamples. The power transmission element 348 may comprise copper wiresor cables. Although FIG. 3 depicts two malleable elements, it isunderstood that the bendable section 332 may comprise one malleableelement or it may comprise more than two malleable elements.

The bendable element 320 (e.g., the bendable section 332) may compriseone or more signal-carrying elements (not shown). The one or moresignal-carrying elements may effectuate data transmission between one ormore components (e.g. the processor 346, the memory 344, or othercircuitry) mounted on or integrated with the PCB 336 and a computingdevice (e.g., a power source) comprising the port or plug with which theplug 334 connects. A port of the computing device or other realizationof the power source may comprise a USB port and the plug 334 of thenetwork device 304 may comprise a mating USB plug. Data signals betweenthe computing device and one or more components of the PCB 336 may becarried via the computing device's USB port, the USB plug 334 of thenetwork device 304, and the one or more signal-carrying elements. Theone or more signal-carrying elements may be integrated with the powertransmission element 348. The one or more signal-carrying elements andthe power transmission element 348 may be realized as a singleelectrical cable, such as a single electrical cable within the bendablesection 332.

FIG. 4 illustrates a cross-sectional view of a bendable section 432(e.g., the bendable section 332 of FIG. 3) of a bendable element of anetwork device. The bendable section 432 may comprise a central powertransmission element 448 flanked on either side by a pair of malleableelements 450. The power transmission element 448 may be configured witha circular cross section. The malleable elements 450 may be configuredwith rectangular cross sections. The power transmission element 448 andthe malleable elements 450 may be similar to or the same as therespective power transmission element 348 and malleable elements 350 ofFIG. 3 in some aspects. The power transmission element 448 and themalleable elements 450 may be encased within an insulating coveringmaterial 451, such as a flexible plastic. Although FIG. 4 depicts twomalleable elements 450, it is understood that the bendable section 432may comprise one malleable element or it may comprise more than twomalleable elements.

FIG. 5 illustrates a perspective view of a network device 504 (e.g., thenetwork device 304 of FIG. 3). The network device 504 may comprise agateway, such as an LPWAN gateway. The network device 504 may comprise abody 530 housing a PCB. The PCB may comprise a transceiver andassociated antenna for wireless communication, such as wirelesscommunication with one or more end nodes. The network device 504 maycomprise a bendable element 520 having a bendable section 532 and a plug534. The plug 534 may be connected to a power source to provideelectrical power for the network device 504. The connection of the plug534 to the power source may additionally or alternatively provide amounting point to support the body 530. The bendable section 532 may bemanipulated (e.g., bent, twisted, etc.) to adjust the position and/ororientation of the body 530 and the antenna within. The bendable section532 is depicted in a flat or ribbon shape, but the disclosure is not solimited. For example, the bendable section 532 may be configured to havea circular, square, or rectangular cross section.

FIG. 6 illustrates a perspective view of a network device 604 (e.g., thenetwork device 304 of FIG. 3) connected to a charger unit 660. Thecharger unit 660, in turn, may be connected to a wall socket 662 toreceive power. The network device 604 may comprise an LPWAN gateway. Thenetwork device 604 may comprise a body 630. The body 630 may house a PCB(e.g., the PCB 336 of FIG. 3) comprising a transceiver and antenna. Thenetwork device 604 may comprise a bendable element having a bendablesection 632 and a plug 634. The plug 634 may be inserted into thecharger unit 660 to carry electrical power to the body 630 of thenetwork device 604 (e.g., the power unit and other components on thePCB) via the bendable section 632. The charger unit 660 may act as thepower source (e.g., the power source 106, 206 of FIGS. 1 and 2,respectively) in this example. In the network device 604 shown in FIG.6, the plug 634 may comprise a USB plug and the charger unit 660 maycomprise a USB wall charger unit configured with a USB port. The chargerunit 660 may comprise two or three prongs (not visible in FIG. 6)inserted into the wall socket 662.

As shown in FIG. 6, the bendable section 632 is bent (e.g., according tooperator manipulation) in such a manner to cause the body 630 to assumean orientation that is perpendicular to the orientation of the plug 634and the port of the charger unit 660. That is, the body 630 isperpendicular to the direction in which the plug 634 is inserted intothe port of the charger unit 660. The configuration of the bendablesection 632 has also caused the body 630 to be positioned closer to thecharger unit 660 and wall socket 662 than if the bendable section 632were straightened.

FIGS. 7A-7E illustrate configurations of a network device 704 (e.g., thenetwork device 304 of FIG. 3) and its bendable section 732. By virtue ofthe properties of the bendable section 732 described herein, the networkdevice 704 may substantially maintain the illustrated position after amanipulating force is removed. In the various views shown in FIGS.7A-7E, the plug 734 is assumed to be in a fixed position, such as may bethe case when connected to a power source. Although the orientation ofthe plug 734 is shown in FIGS. 7A-7E as being horizontal, such as if theconnected-to port is on a side surface of the power source, thedisclosure is not so limited. For example, the plug 734 may connect to aport on a top surface or an angled surface of the power source.

FIGS. 7A-7D show the network device 704 from a side view and FIG. 7Eshows the network device 704 from a top view, as indicated by therespective set of three-dimensional (X, Y, Z) coordinate linesaccompanying each figure. If considered with respect to the dimensionsof the body 730, the X-axis corresponds to the length-wise dimension ofthe body 730, the Y-axis corresponds to the height-wise dimension of thebody 730, and the Z-axis corresponds to the width-wise dimension of thebody 730.

In FIG. 7A, the bendable section 732 is positioned in a straightenedconfiguration. For purposes of the discussion of FIGS. 7B-7E, theposition of the body 730 may be considered neutral with respect to theX-, Y-, and Z-axes. For example, the positions of the body 730 andbendable section 732 in FIG. 7A may be considered as initial positionsand the positions of the body 730 and bendable section in FIGS. 7A-7Emay be considered adjusted positions.

In FIG. 7B, the bendable section 732 is configured to bend downward,causing the body 730 to rotate outward from the plug 734 and shiftdownward from the plug 734. That is, the body 730 is rotatedcounter-clockwise about the Z-axis and moved downward on the Y-axis. Therotation of the body 730 in FIG. 7B may be also seen as an adjustment tothe orientation of the body 730 with respect to the width-wise axis ofthe body. The positioning shown in FIG. 7B would also cause a minorshift toward the plug 734 on the X-axis.

In FIG. 7C, the bendable section 732 is configured in an S-like shape,causing the body 730 to move toward the plug 734 (i.e., backward) on theX-axis and downward from the plug 734 on the Y-axis. Relative to thepositioning shown in FIG. 7A, no rotation of the body 730 is exhibitedin FIG. 7C.

In FIG. 7D, the bendable section 732 is subject to a twistingmanipulation. In particular, the bendable section 732 is twistedlength-wise by 90 degrees relative to the positioning shown in FIG. 7A,causing a like rotation of the body 730. That is, the body 730 isrotated about the X-axis. The rotation of the body 730 in FIG. 7D may bealso seen as an adjustment to the orientation of the body 730 withrespect to the length-wise axis of the body.

In FIG. 7E (a top-down view of the network device 704), the bendablesection 732 is configured to bend sideward, causing a sideward shift androtation (i.e., a height-wise rotation) of the body 730. That is, thebody 730 is shifted along the Z-axis and rotated about the Y-axis. Therotation of the body 730 in FIG. 7E may be also seen as an adjustment tothe orientation of the body 730 with respect to the height-wise axis ofthe body. The positioning shown in FIG. 7E would also cause a minorshift of the body 730 toward the plug 734 on the X-axis.

The configurations and positionings of the bendable section 732 and body730 shown in FIG. 7A-7E are only examples of the many possibleconfigurations and positionings. The body 730 may be positionedaccording to any combination of an upward/downward shift (e.g., a shiftalong the Y-axis), a forward/backward shift (e.g., a shift along theX-axis), a side-to-side shift (e.g., a shift along the Z-axis), alength-wise rotation (e.g., a rotation about the X-axis), a height-wiserotation (e.g., a rotation about the Y-axis), and a width-wise rotation(e.g., a rotation about the Z-axis). For example, the body 730 may beboth shifted and rotated. For example, the body 730 may be rotatedaround both a first axis and a second axis of the body 730 (and even athird axis of the body 730). For example, the body 730 may be shiftedboth upward and side-to-side (and even toward or away from the plug734).

By virtue of these many possible configurations of the bendable section732, the antenna within the body 730 may be faced in virtually anydirection. This may enable optimal or improved RF reception and/ortransmission for the antenna (e.g., RF signal spread). Further, thevarious possible configurations of the bendable section 732 may allowthe network device 704 to accommodate for any space restrictions orchallenges caused by the placement of the power source port to which theplug 734 connects, the placement generally of the power source, or theplacement of any other equipment in the vicinity of the power source.

FIG. 8 depicts a computing device in which the systems, methods, anddevices disclosed herein, or all or some aspects thereof, may beembodied. For example, components such as the first computing device110, network device 104, power source 106, and second computing device108 of FIG. 1, the end nodes 210, gateway 204, power source 206, radiocontroller 214, and application servers of FIG. 2, the network device304 of FIG. 3, the network device 504 of FIG. 5, the network device 604of FIG. 6, and the network device 704 of FIGS. 7A-7E may be implementedgenerally in a computing device, such as the computing device 800 ofFIG. 8. The computing device of FIG. 8 may be all or part of a server,workstation, desktop computer, laptop, tablet, network appliance, PDA,e-reader, digital cellular phone, set top box, or the like, and may beutilized to implement any of the aspects of the systems, methods, anddevices described herein.

The computing device 800 may include a baseboard, or “motherboard,”which is a printed circuit board to which a multitude of components ordevices may be connected by way of a system bus or other electricalcommunication paths. One or more central processing units (CPUs) 804 mayoperate in conjunction with a chipset 806. The CPU(s) 804 may bestandard programmable processors that perform arithmetic and logicaloperations necessary for the operation of the computing device 800.

The CPU(s) 804 may perform the necessary operations by transitioningfrom one discrete physical state to the next through the manipulation ofswitching elements that differentiate between and change these states.Switching elements may generally include electronic circuits thatmaintain one of two binary states, such as flip-flops, and electroniccircuits that provide an output state based on the logical combinationof the states of one or more other switching elements, such as logicgates. These basic switching elements may be combined to create morecomplex logic circuits including registers, adders-subtractors,arithmetic logic units, floating-point units, and the like.

The CPU(s) 804 may be augmented with or replaced by other processingunits, such as GPU(s) 805. The GPU(s) 805 may comprise processing unitsspecialized for but not necessarily limited to highly parallelcomputations, such as graphics and other visualization-relatedprocessing.

A chipset 806 may provide an interface between the CPU(s) 804 and theremainder of the components and devices on the baseboard. The chipset806 may provide an interface to a random access memory (RAM) 808 used asthe main memory in the computing device 800. The chipset 806 may furtherprovide an interface to a computer-readable storage medium, such as aread-only memory (ROM) 820 or non-volatile RAM (NVRAM) (not shown), forstoring basic routines that may help to start up the computing device800 and to transfer information between the various components anddevices. ROM 820 or NVRAM may also store other software componentsnecessary for the operation of the computing device 800 in accordancewith the aspects described herein.

The computing device 800 may operate in a networked environment usinglogical connections to remote computing nodes and computer systemsthrough local area network (LAN) 816. The chipset 806 may includefunctionality for providing network connectivity through a networkinterface controller (NIC) 822, such as a gigabit Ethernet adapter. ANIC 822 may be capable of connecting the computing device 800 to othercomputing nodes over a network 816. It should be appreciated thatmultiple NICs 822 may be present in the computing device 800, connectingthe computing device to other types of networks and remote computersystems.

The computing device 800 may be connected to a mass storage device 828that provides non-volatile storage for the computer. The mass storagedevice 828 may store system programs, application programs, otherprogram modules, and data, which have been described in greater detailherein. The mass storage device 828 may be connected to the computingdevice 800 through a storage controller 824 connected to the chipset806. The mass storage device 828 may consist of one or more physicalstorage units. A storage controller 824 may interface with the physicalstorage units through a serial attached SCSI (SAS) interface, a serialadvanced technology attachment (SATA) interface, a fiber channel (FC)interface, or other type of interface for physically connecting andtransferring data between computers and physical storage units.

The computing device 800 may store data on a mass storage device 828 bytransforming the physical state of the physical storage units to reflectthe information being stored. The specific transformation of a physicalstate may depend on various factors and on different implementations ofthis description. Examples of such factors may include, but are notlimited to, the technology used to implement the physical storage unitsand whether the mass storage device 828 is characterized as primary orsecondary storage and the like.

For example, the computing device 800 may store information to the massstorage device 828 by issuing instructions through a storage controller824 to alter the magnetic characteristics of a particular locationwithin a magnetic disk drive unit, the reflective or refractivecharacteristics of a particular location in an optical storage unit, orthe electrical characteristics of a particular capacitor, transistor, orother discrete component in a solid-state storage unit. Othertransformations of physical media are possible without departing fromthe scope and spirit of the present description, with the foregoingexamples provided only to facilitate this description. The computingdevice 800 may further read information from the mass storage device 828by detecting the physical states or characteristics of one or moreparticular locations within the physical storage units.

In addition to the mass storage device 828 described above, thecomputing device 800 may have access to other computer-readable storagemedia to store and retrieve information, such as program modules, datastructures, or other data. It should be appreciated by those skilled inthe art that computer-readable storage media may be any available mediathat provides for the storage of non-transitory data and that may beaccessed by the computing device 800.

By way of example and not limitation, computer-readable storage mediamay include volatile and non-volatile, transitory computer-readablestorage media and non-transitory computer-readable storage media, andremovable and non-removable media implemented in any method ortechnology. Computer-readable storage media includes, but is not limitedto, RAM, ROM, erasable programmable ROM (“EPROM”), electrically erasableprogrammable ROM (“EEPROM”), flash memory or other solid-state memorytechnology, compact disc ROM (“CD-ROM”), digital versatile disk (“DVD”),high definition DVD (“HD-DVD”), BLU-RAY, or other optical storage,magnetic cassettes, magnetic tape, magnetic disk storage, other magneticstorage devices, or any other medium that may be used to store thedesired information in a non-transitory fashion.

A mass storage device, such as the mass storage device 828 depicted inFIG. 8, may store an operating system utilized to control the operationof the computing device 800. The operating system may comprise a versionof the LINUX operating system. The operating system may comprise aversion of the WINDOWS SERVER operating system from the MICROSOFTCorporation. According to further aspects, the operating system maycomprise a version of the UNIX operating system. Various mobile phoneoperating systems, such as IOS and ANDROID, may also be utilized. Itshould be appreciated that other operating systems may also be utilized.The mass storage device 828 may store other system or applicationprograms and data utilized by the computing device 800.

The mass storage device 828 or other computer-readable storage media mayalso be encoded with computer-executable instructions, which, whenloaded into the computing device 800, transforms the computing devicefrom a general-purpose computing system into a special-purpose computercapable of implementing the aspects described herein. Thesecomputer-executable instructions transform the computing device 800 byspecifying how the CPU(s) 804 transition between states, as describedabove. The computing device 800 may have access to computer-readablestorage media storing computer-executable instructions, which, whenexecuted by the computing device 800, may perform the methods describedherein.

A computing device, such as the computing device 800 depicted in FIG. 8,may also include an input/output controller 832 for receiving andprocessing input from a number of input devices, such as a keyboard, amouse, a touchpad, a touch screen, an electronic stylus, or other typeof input device. Similarly, an input/output controller 832 may provideoutput to a display, such as a computer monitor, a flat-panel display, adigital projector, a printer, a plotter, or other type of output device.It will be appreciated that the computing device 800 may not include allof the components shown in FIG. 8, may include other components that arenot explicitly shown in FIG. 8, or may utilize an architecturecompletely different than that shown in FIG. 8.

As described herein, a computing device may be a physical computingdevice, such as the computing device 800 of FIG. 8. A computing node mayalso include a virtual machine host process and one or more virtualmachine instances. Computer-executable instructions may be executed bythe physical hardware of a computing device indirectly throughinterpretation and/or execution of instructions stored and executed inthe context of a virtual machine.

It is to be understood that the systems, methods, and devices are notlimited to specific methods, specific components, or to particularimplementations. It is also to be understood that the terminology usedherein is for the purpose of describing particular embodiments only andis not intended to be limiting.

As used in the specification and the appended claims, the singular forms“a,” “an,” and “the” include plural referents unless the context clearlydictates otherwise. Ranges may be expressed herein as from “about” oneparticular value, and/or to “about” another particular value. When sucha range is expressed, another embodiment includes from the oneparticular value and/or to the other particular value. Similarly, whenvalues are expressed as approximations, by use of the antecedent“about,” it will be understood that the particular value forms anotherembodiment. It will be further understood that the endpoints of each ofthe ranges are significant both in relation to the other endpoint, andindependently of the other endpoint.

“Optional” or “optionally” means that the subsequently described eventor circumstance may or may not occur, and that the description includesinstances where said event or circumstance occurs and instances where itdoes not.

Throughout the description and claims of this specification, the word“comprise” and variations of the word, such as “comprising” and“comprises,” means “including but not limited to,” and is not intendedto exclude, for example, other components, integers or steps.“Exemplary” means “an example of” and is not intended to convey anindication of a preferred or ideal embodiment. “Such as” is not used ina restrictive sense, but for explanatory purposes.

Components are described that may be used to perform the describedsystems, methods, and devices. When combinations, subsets, interactions,groups, etc., of these components are described, it is understood thatwhile specific references to each of the various individual andcollective combinations and permutations of these may not be explicitlydescribed, each is specifically contemplated and described herein, forall systems, methods, and devices. This applies to all aspects of thisapplication including, but not limited to, operations in describedmethods. Thus, if there are a variety of additional operations that maybe performed it is understood that each of these additional operationsmay be performed with any specific embodiment or combination ofembodiments of the described methods.

As will be appreciated by one skilled in the art, the systems, methods,and devices may take the form of an entirely hardware embodiment, anentirely software embodiment, or an embodiment combining software andhardware aspects. Furthermore, the systems, methods, and devices maytake the form of a computer program product on a computer-readablestorage medium having computer-readable program instructions (e.g.,computer software) embodied in the storage medium. More particularly,the present systems, methods, and devices may take the form ofweb-implemented computer software. Any suitable computer-readablestorage medium may be utilized including hard disks, CD-ROMs, opticalstorage devices, or magnetic storage devices.

Embodiments of the systems, methods, and devices are described belowwith reference to block diagrams and flowchart illustrations of methods,systems, apparatuses and computer program products. It will beunderstood that each block of the block diagrams and flowchartillustrations, and combinations of blocks in the block diagrams andflowchart illustrations, respectively, may be implemented by computerprogram instructions. These computer program instructions may be loadedon a general-purpose computer, special-purpose computer, or otherprogrammable data processing apparatus to produce a machine, such thatthe instructions which execute on the computer or other programmabledata processing apparatus create a means for implementing the functionsspecified in the flowchart block or blocks.

These computer program instructions may also be stored in acomputer-readable memory that may direct a computer or otherprogrammable data processing apparatus to function in a particularmanner, such that the instructions stored in the computer-readablememory produce an article of manufacture including computer-readableinstructions for implementing the function specified in the flowchartblock or blocks. The computer program instructions may also be loadedonto a computer or other programmable data processing apparatus to causea series of operational steps to be performed on the computer or otherprogrammable apparatus to produce a computer-implemented process suchthat the instructions that execute on the computer or other programmableapparatus provide steps for implementing the functions specified in theflowchart block or blocks.

The various features and processes described above may be usedindependently of one another, or may be combined in various ways. Allpossible combinations and sub-combinations are intended to fall withinthe scope of this disclosure. In addition, certain methods or processblocks may be omitted in some implementations. The methods and processesdescribed herein are also not limited to any particular sequence, andthe blocks or states relating thereto may be performed in othersequences that are appropriate. For example, described blocks or statesmay be performed in an order other than that specifically described, ormultiple blocks or states may be combined in a single block or state.The example blocks or states may be performed in serial, in parallel, orin some other manner. Blocks or states may be added to or removed fromthe described example embodiments. The example systems and componentsdescribed herein may be configured differently than described. Forexample, elements may be added to, removed from, or rearranged comparedto the described example embodiments.

It will also be appreciated that various items are illustrated as beingstored in memory or on storage while being used, and that these items orportions thereof may be transferred between memory and other storagedevices for purposes of memory management and data integrity.Alternatively, in other embodiments, some or all of the software modulesand/or systems may execute in memory on another device and communicatewith the illustrated computing systems via inter-computer communication.Furthermore, in some embodiments, some or all of the systems and/ormodules may be implemented or provided in other ways, such as at leastpartially in firmware and/or hardware, including, but not limited to,one or more application-specific integrated circuits (“ASICs”), standardintegrated circuits, controllers (e.g., by executing appropriateinstructions, and including microcontrollers and/or embeddedcontrollers), field-programmable gate arrays (“FPGAs”), complexprogrammable logic devices (“CPLDs”), etc. Some or all of the modules,systems, and data structures may also be stored (e.g., as softwareinstructions or structured data) on a computer-readable medium, such asa hard disk, a memory, a network, or a portable media article to be readby an appropriate device or via an appropriate connection. The systems,modules, and data structures may also be transmitted as generated datasignals (e.g., as part of a carrier wave or other analog or digitalpropagated signal) on a variety of computer-readable transmission media,including wireless-based and wired/cable-based media, and may take avariety of forms (e.g., as part of a single or multiplexed analogsignal, or as multiple discrete digital packets or frames). Suchcomputer program products may also take other forms in otherembodiments. Accordingly, the present invention may be practiced withother computer system configurations.

While the systems, methods, and devices have been described inconnection with preferred embodiments and specific examples, it is notintended that the scope be limited to the particular embodiments setforth, as the embodiments herein are intended in all respects to beillustrative rather than restrictive.

Unless otherwise expressly stated, it is in no way intended that anymethod set forth herein be construed as requiring that its operations beperformed in a specific order. Accordingly, where a method claim doesnot actually recite an order to be followed by its operations or it isnot otherwise specifically stated in the claims or descriptions that theoperations are to be limited to a specific order, it is no way intendedthat an order be inferred, in any respect. This holds for any possiblenon-express basis for interpretation, including: matters of logic withrespect to arrangement of steps or operational flow; plain meaningderived from grammatical organization or punctuation; and the number ortype of embodiments described in the specification.

It will be apparent to those skilled in the art that variousmodifications and variations may be made without departing from thescope or spirit of the present disclosure. Other embodiments will beapparent to those skilled in the art from consideration of thespecification and practices described herein. It is intended that thespecification and example figures be considered as exemplary only, witha true scope and spirit being indicated by the following claims.

What is claimed is:
 1. A network device comprising: a body comprising anantenna configured to enable radio frequency (RF) communication; and abendable element attached to the body and configured to carry electricalpower to the body, wherein the bendable element is further configuredfor variable positioning, a positioning of the bendable element issubstantially maintained upon removal of a positioning force, and afacing of the antenna is based on the positioning of the bendableelement.
 2. The network device of claim 1, wherein performance of theantenna in at least one of RF reception or RF transmission is based onthe facing of the antenna.
 3. The network device of claim 1, wherein thebendable element comprises a plug at an end of the bendable elementdistal from an attachment point of the bendable element to the body,wherein the plug is configured to receive electrical power from a powersource.
 4. The network device of claim 3, wherein the plug is configuredto connect to a port of the power source and the connection of the plugto the port physically supports, at least in part, the network device.5. The network device of claim 4, wherein the power source comprises acharger unit.
 6. The network device of claim 4, wherein the power sourcecomprises at least one of a wireless router, a wireless gateway, awireless access point, a cable modem, a digital subscriber line (DSL)modem, or a set-top box.
 7. The network device of claim 3, wherein theplug comprises a universal serial bus (USB) plug.
 8. The network deviceof claim 1, wherein: the bendable element is configured to adjust aposition of the body in at least one of a direction corresponding to alength-wise dimension of the body, a direction corresponding to awidth-wise dimension of the body, or a direction corresponding to aheight-wise dimension of the body, and the bendable element isconfigured to adjust an orientation of the body with respect to at leastone of a length-wise axis of the body, a height-wise axis of the body,or a width-wise axis of the body.
 9. The network device of claim 1,wherein: the bendable element is configured to adjust a position of thebody in at least two of a direction corresponding to a length-wisedimension of the body, a direction corresponding to a width-wisedimension of the body, or a direction corresponding to a height-wisedimension of the body, and the bendable element is configured to adjustan orientation of the body with respect to at least two of a length-wiseaxis of the body, a height-wise axis of the body, or a width-wise axisof the body.
 10. The network device of claim 1, wherein: the bendableelement is configured to adjust a position of the body in each of adirection corresponding to a length-wise dimension of the body, adirection corresponding to a width-wise dimension of the body, and adirection corresponding to a height-wise dimension of the body, and thebendable element is configured to adjust an orientation of the body withrespect to each of a length-wise axis of the body, a height-wise axis ofthe body, and a width-wise axis of the body.
 11. The network device ofclaim 1, wherein the network device is configured as a gateway for a lowpower wire area network (LPWAN).
 12. The network device of claim 11,wherein the network device is configured to communicate, via theantenna, with one or more end nodes of the LPWAN.
 13. The network deviceof claim 12, wherein the network device is configured to communicatewith the one or more end nodes via a protocol comprising at least one ofZigbee, Z-Wave, Wi-Fi HaLow, NB-IoT, DASH7, Sigfox, or LoRa.
 14. Thenetwork device of claim 1, wherein the bendable element comprises amalleable element via which a positioning of the bendable element issubstantially maintained and a power transmission element via which theelectrical power is carried to the body.
 15. A network devicecomprising: a body; a printed circuit board (PCB) housed within the bodyand comprising an antenna configured to enable radio frequency (RF)communication; and a bendable element comprising an elongate bendablesection and a plug configured to receive electrical power, wherein aproximate end of the bendable section is attached to and physicallysupports the body and a distal end of the bendable section is configuredwith the plug, wherein the bendable section comprises a powertransmission element electrically connecting the plug with a power unitassociated with the PCB and at least one malleable element via which avariable positioning of the bendable section is substantially maintainedupon removal of a positioning force.
 16. The network device of claim 15,wherein the plug comprises a universal serial bus (USB) plug.
 17. Thenetwork device of claim 15, wherein the antenna comprises at least oneof a microstrip antenna, a patch antenna, an inverted-F antenna, or aplanar inverted-F antenna (PIFA).
 18. The network device of claim 17,wherein a planar surface of the antenna corresponds with a planarsurface of the PCB.
 19. The network device of claim 15, wherein the atleast one malleable element spans at least a majority of a length of thebendable section.
 20. The network device of claim 15, wherein the atleast one malleable element comprises at least one of aluminum, analuminum alloy, copper, or a copper alloy.